Issue #27 Completing activation of the security TCK. #46
Conversation
…not authentication Disable running the new security tck to allow test runs to focus on getting the old security TCK to run properly
…dant patching.
|
FYI the failures are expected until we have a new release of WildFly. One failure still needs challenging to see if we can agree to ignore but we have discussed that the reason for the failure is not actually the purpose of that test. |
| @@ -211,7 +212,7 @@ then | |||
| echo "Configuring WildFly for the Old TCK" | |||
| pushd $TS_HOME/bin | |||
| $ANT_HOME/bin/ant config.vi | |||
There was a problem hiding this comment.
@darranl It seems the various uses of $ANT_HOME/bin is not necessary. If so we should clean that out having the mix of usage is confusing. That shouldn't block this though.
|
@darranl Just an FYI. This currently runs tests against the latest successful build of the Nightly WildFly CI job. Should it be passing on last nights main branch? |
|
@jamezp The nightly job last night had 1 failure and thus didn't publish the artifact. Last successful run was against wildfly/wildfly@62f0e67 which doesn't include wildfly/wildfly#15968 |
No description provided.