Add proper labeling and java run stage#777
Conversation
vjovanov
force-pushed
the
vj/gh-760-failure-classification
branch
from
fbf5b2d to
b8c00e0
Compare
|
|
||
| jobs: | ||
| get-all-metadata: | ||
| if: github.repository == 'oracle/graalvm-reachability-metadata' |
There was a problem hiding this comment.
Do we want to run this job on master push on forks (but not the test-all-metadata and all-metadata-passed)?
There was a problem hiding this comment.
This one is not automatic, just manual. Although I have a follow up PR:
https://github.com/oracle/graalvm-reachability-metadata/pulls
There was a problem hiding this comment.
But it should still trigger on pushes to master (even on a fork), no? The test-all-metadata and all-metadata-passed jobs are still behind if: github.repository == 'oracle/graalvm-reachability-metadata' checks, but the get-all-metadata job isn't. Is this by design?
|
|
||
| jobs: | ||
| get-changed-metadata: | ||
| if: github.repository == 'oracle/graalvm-reachability-metadata' |
There was a problem hiding this comment.
Same question as for test-all-metadata.yml.
vjovanov
force-pushed
the
vj/gh-760-failure-classification
branch
2 times, most recently
from
71518c5 to
437b761
Compare
vjovanov
force-pushed
the
vj/gh-760-failure-classification
branch
from
437b761 to
e60f7c9
Compare
2 participants
What does this PR do?
Does smarter bisecting when running automated tests. Check if it works first, and only if it fails do the bisecting. Also, adds a new category
java runand applies labels.Also, increases the frequency of running the testing job to daily.
Fixes: #760