ubuntu-kernel-tests

Test case blacklisting is not working for AWS / GCP

Bug #1839405 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Critical
Sean Feole

Bug Description

As we already have the blacklist file: blacklist.disco

This should be skipped, however it's not, this needs to be investigated.

Po-Hsu Lin (cypressyew)
tags: added: sru-20190722
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

The same applies to zram_smoke test, quota test.

They have been blacklisted for aws: blacklist.aws

Revision history for this message
Po-Hsu Lin (cypressyew) wrote : Re: Test case blacklisting is not working for AWS

This is affect the fan smoke test in Trusty 4.4 AWS as well, it looks like this has something to with the test infrastructure code. Adjust the title accordingly

summary: - libhugetlbfs was not skipped for D-AWS
+ Test case blacklisting is not working for AWS
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Issue found on GCP cloud as well.

tags: added: gcp
Po-Hsu Lin (cypressyew)
summary: - Test case blacklisting is not working for AWS
+ Test case blacklisting is not working for AWS / GCP
Revision history for this message
Sean Feole (sfeole) wrote :

I've taken a look at the code on both clouds and believe i resolved this problem.
The autotest-client-tests directory was moved out of $HOMEDIR for the jenkins user, hence unable to parse what tests needed to be blacklisted.

After re-running the master jobs on each cloud, they now appear to be honoring their assigned rules.

Changed in ubuntu-kernel-tests:
status: New → Fix Released
assignee: nobody → Sean Feole (sfeole)
importance: Undecided → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.