Repo name > 32 characters causes " Deserialization failure" error in dashboard view

Bug #1223721 reported by Andrew McDermott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LAVA Server
Confirmed
Medium
Antonio Terceiro

Bug Description

A repo name > 32 characters causes a "Deserialization failure"

I have a YAML file that has:

install:
  git-repos:
    - git://spicy/scratch/jtreg-bin
    - git://spicy/scratch/openjdk8-aarch64-prebuilt-tests (**** this is OK)
    - git://spicy/scratch/oe/test-definitions

which works fine.

If I change this to (as I did):

install:
  git-repos:
    - git://spicy/scratch/jtreg-bin
    - git://spicy/scratch/openjdk8-aarch64-snapshot-test-archive (**** this causes an error)
    - git://spicy/scratch/oe/test-definitions

then I get the following error when viewing the results in the Dashboard:

Cause

value too long for type character varying(32)

Deserialization failure traceback

Traceback (most recent call last):
  File "/srv/lava/.<email address hidden>/dashboard_app/models.py", line 497, in deserializeself._do_deserialize(prefer_evolution)
  File "/srv/lava/.<email address hidden>/dashboard_app/models.py", line 518, in _do_deserializehelper.deserialize(self,prefer_evolution)
  File "/srv/lava/.<email address hidden>/dashboard_app/helpers.py", line 847, in deserializeimporter().import_document(s_bundle,doc)
  File "/srv/lava/.<email address hidden>/dashboard_app/helpers.py", line 65, in import_documentself._import_document_with_transaction(s_bundle,doc)
  File "/srv/lava/.cache/eggs/Django-1.4.2-py2.7.egg/django/db/transaction.py", line 209, in innerreturnfunc(*args,**kwargs)
  File "/srv/lava/.<email address hidden>/dashboard_app/helpers.py", line 107, in _import_document_with_transactionself._import_document(s_bundle,doc)
  File "/srv/lava/.<email address hidden>/dashboard_app/helpers.py", line 111, in _import_documentself._import_test_run(c_test_run,s_bundle)
  File "/srv/lava/.<email address hidden>/dashboard_app/helpers.py", line 710, in _import_test_runs_test_run=super(BundleFormatImporter_1_4,self)._import_test_run(c_test_run,s_bundle)
  File "/srv/lava/.<email address hidden>/dashboard_app/helpers.py", line 694, in _import_test_runs_test_run=super(BundleFormatImporter_1_3,self)._import_test_run(c_test_run,s_bundle)
  File "/srv/lava/.<email address hidden>/dashboard_app/helpers.py", line 159, in _import_test_runself._import_software_context(c_test_run,s_test_run)
  File "/srv/lava/.<email address hidden>/dashboard_app/helpers.py", line 621, in _import_software_contextself._import_sources(c_test_run,s_test_run)
  File "/srv/lava/.<email address hidden>/dashboard_app/helpers.py", line 656, in _import_sourceselseNone)
  File "/srv/lava/.cache/eggs/Django-1.4.2-py2.7.egg/django/db/models/manager.py", line 134, in get_or_createreturnself.get_query_set().get_or_create(**kwargs)
  File "/srv/lava/.cache/eggs/Django-1.4.2-py2.7.egg/django/db/models/query.py", line 452, in get_or_createobj.save(force_insert=True,using=self.db)
  File "/srv/lava/.cache/eggs/Django-1.4.2-py2.7.egg/django/db/models/base.py", line 463, in saveself.save_base(using=using,force_insert=force_insert,force_update=force_update)
  File "/srv/lava/.cache/eggs/Django-1.4.2-py2.7.egg/django/db/models/base.py", line 551, in save_baseresult=manager._insert([self],fields=fields,return_id=update_pk,using=using,raw=raw)
  File "/srv/lava/.cache/eggs/Django-1.4.2-py2.7.egg/django/db/models/manager.py", line 203, in _insertreturninsert_query(self.model,objs,fields,**kwargs)
  File "/srv/lava/.cache/eggs/Django-1.4.2-py2.7.egg/django/db/models/query.py", line 1593, in insert_queryreturnquery.get_compiler(using=using).execute_sql(return_id)
  File "/srv/lava/.cache/eggs/Django-1.4.2-py2.7.egg/django/db/models/sql/compiler.py", line 910, in execute_sqlcursor.execute(sql,params)
  File "/srv/lava/.cache/eggs/Django-1.4.2-py2.7.egg/django/db/backends/postgresql_psycopg2/base.py", line 52, in executereturnself.cursor.execute(query,args)DatabaseError: value too long for type character varying(32)

My local LAVA install was done from scratch as of this morning (Wed Sep 11 2013).

Revision history for this message
Andrew McDermott (frobware) wrote :
Changed in lava-dashboard:
importance: Undecided → Medium
Changed in lava-dashboard:
assignee: nobody → Antonio Terceiro (terceiro)
status: New → Confirmed
affects: lava-dashboard → lava-server
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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