You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For OpenJ9 builds, the openj9 sha used to compile the SDK should be passed to test. Sometimes there are code changes with matching test changes. If such a change is merged "mid-flight" (ie. After a compile starts but before a test starts), the test job would pickup the change and could cause failure. This has happened in eclipse-openj9/openj9#12629 for example.
The text was updated successfully, but these errors were encountered:
I think this is valid.
In addition, I think we should do a sniff for all test-related repos and pass all test repo SHAs to test builds to ensure we are running the same test materials in one pipeline. Otherwise, we would have a similar problem. If a PR is delivered between test builds, we could end up running different test materials in the same pipeline.
For OpenJ9 builds, the openj9 sha used to compile the SDK should be passed to test. Sometimes there are code changes with matching test changes. If such a change is merged "mid-flight" (ie. After a compile starts but before a test starts), the test job would pickup the change and could cause failure. This has happened in eclipse-openj9/openj9#12629 for example.
The text was updated successfully, but these errors were encountered: